Method and system for managing the lifecycles of media assets

ABSTRACT

There is provided a method for managing the lifecycles of one or more media assets. The method comprises importing the one or more media assets into a system for managing the lifecycles of the one or more media assets, determining one or more metadata tags for association with the one or more media assets by evaluating the one or more media assets with one or more tagging filters, associating the one or more metadata tags with the one or more media assets after determining one or more metadata tags for association with the one or more media assets, and grouping the one or more media assets according to the one or more metadata tags associated with the one or more media assets by evaluating the one or more metadata tags with one or more grouping filters to generate one or more media asset groups.

BACKGROUND OF THE INVENTION

1. Field of the Invention

The present invention relates generally to media asset management. More particularly, the present invention relates to media asset lifecycle management.

2. Background Art

The creation rate of media assets such as audio recordings, pictures, and videos has increased tremendously because of the proliferation of digital recording and communication systems. Before this proliferation, the restricted availability of the means of producing and copying media assets meant that managing such media assets' lifecycles was relatively straightforward. Ad-hoc or manual processes were adequate for the purposes of deciding if a given media asset violated a copyright law, went against a decency guideline, or was simply no longer relevant and required deletion. Now, however, those processes tend to be overwhelmed by the flood of media assets that are created with the aid of modern technology.

The problem of media asset lifecycle management is distinct from the problem of storing such media assets. In the present state of the art, storage of media assets can be accomplished by digital content management systems, which absorb the modern content flood with relative ease, thanks to advances in areas such as hard disk drive design and relational database design. Once the media assets are stored, however, managing them over the course of their lifecycle (e.g., deciding if a particular picture is indecent, or if a particular recording contains a segment of a copyrighted work) is a difficult problem, conventional solutions to which remain rooted in old practices.

For example, several user-submitted content web sites, such as Youtube, manage very large sets of media assets in the form of user-submitted videos. The lifecycle of an exemplary video on such a website can involve import or upload processing, decency guideline violation reviewing, copyright guideline violation reviewing, and possibly deletion or elevation to a ranked or featured status. In order to review every user-submitted video for copyright violations, for example, the website can implement a variety of ad-hoc or manual processes. It can employ an army of human reviewers to look at each user-submitted video. Alternatively, it can demand copyrighted material from copyright holders to compare with its user-submitted videos in a brute-force manner. Neither of these processes scale well to manage the modern flood of user-submitted video content. Thus, the website may simply resort to waiting for a copyright holder to take some action, such as threatening or instituting a legal action, which entails major issues.

Accordingly, there is a need to overcome the drawbacks and deficiencies in the art by providing an improved method and system for managing the lifecycle of media assets.

SUMMARY OF THE INVENTION

There is provided a method and system for managing the lifecycles of media assets, substantially as shown in and/or described in connection with at least one of the figures, as set forth more completely in the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

The features and advantages of the present invention will become more readily apparent to those ordinarily skilled in the art after reviewing the following detailed description and accompanying drawings, wherein:

FIG. 1 shows a diagram of an exemplary system for managing the lifecycles of media assets, according to one embodiment of the present invention;

FIG. 2 shows a diagram of an exemplary system for managing the lifecycles of media assets, according to one embodiment of the present invention; and

FIG. 3 is a flowchart presenting a method of managing the lifecycles of media assets, according to one embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

The present application is directed to a method and system for managing the lifecycles of media assets. The following description contains specific information pertaining to the implementation of the present invention. One skilled in the art will recognize that the present invention may be implemented in a manner different from that specifically discussed in the present application. Moreover, some of the specific details of the invention are not discussed in order not to obscure the invention. The specific details not described in the present application are within the knowledge of a person of ordinary skill in the art. The drawings in the present application and their accompanying detailed description are directed to merely exemplary embodiments of the invention. To maintain brevity, other embodiments of the invention, which use the principles of the present invention, are not specifically described in the present application and are not specifically illustrated by the present drawings. It should be borne in mind that, unless noted otherwise, like or corresponding elements among the figures may be indicated by like or corresponding reference numerals.

FIG. 1 shows a diagram of system 100 including media asset lifecycle manager (MALM) 140 for managing the lifecycle of media assets, according to one embodiment of the present invention. MALM 140, in this configuration, imports pictures, searches pictures for royalty-triggering content, and exports pictures for publication. In operation, camera 104, which may be, for example, a film camera or a digital camera, generates pictures 106 a through 110 a of scene 102. Scene 102 may be, for example, a view of guests and a costumed employee in a theme park, and camera 104 may be operated automatically or by a person, for example by another theme park employee.

Pictures 106 a through 110 a are, in this example, associated with metadata tags 112 a through 116 a. In particular, picture 106 a is associated with metadata tag 112 a, picture 108 a is associated with metadata tag 114 a, and picture 110 a is associated with metadata tag 116 a. As camera 104 generates pictures 106 a through 110 a, camera 104 may simultaneously generate and associate metadata tags 112 a through 116 a. In metadata tags 112 a through 116 a, camera 104 may record an identification tag, for example, a picture sequence number, a timestamp, or a location in the theme park where associated pictures 106 a through 110 a were taken. Camera 104 may contain pictures and metadata tags 106 a through 116 a internally in, for example, a digital memory or a roll of film. Alternatively, camera 104 may instead transmit pictures and metadata tags 106 a through 116 a to an external storage location (not shown).

Pictures and metadata tags 106 a through 116 a may be imported into MALM 140 by a variety of means. For example, pictures and metadata tags 106 a through 116 a may be imported into MALM 140 through an electrical connection between a memory in camera 104 and a memory in MALM 140, through a wireless connection between a radio device in camera 104 and a radio device in MALM 140, or via an external storage device (such as a flash-memory card, not shown). Pictures and metadata tags 106 a through 116 a may be imported simultaneously, or in separate sessions or transactions. Once imported, pictures and metadata tags 106 a through 116 a may be managed by utilizing various filters and/or an executive included in the present embodiment of MALM 140, such as tagging filter 142, grouping filter 144, and executive 146.

Inside MALM 140, pictures and metadata tags 106 b through 116 b correspond to pictures and metadata tags 106 a through 116 a after importation and subsequent evaluation by tagging filter 142. Tagging filter 142 may evaluate pictures and metadata tags 106 a through 116 a, after importation into MALM 140, in a variety of ways. For example, tagging filter 142 may evaluate picture 106 a and associated metadata tag 112 a to determine if one or more additional metadata tags should be associated, or if already-associated metadata tag 112 a should be disassociated and removed. To make such an evaluation, tagging filter 142 may utilize the information in picture 106 a, the information in metadata tag 112 a, or both. Tagging filter 142 may obtain the information in picture 106 a, for example, by utilizing a computerized image processing of pictures 106 a and comparison other information or pictures a database. Alternatively, tagging filter 142 may utilize information from other sources to evaluate picture 106 a and metadata tag 112 a; for example, tagging filter 142 might utilize information in pictures 108 a and 110 a. Tagging filter 142 may evaluate picture 106 a to determine, for example, if picture 106 a contains copyrighted material, violates a decency policy, or satisfies some other criteria.

In the present embodiment, tagging filter 142 is configured to determine if later publication of pictures 106 a through 110 a will trigger royalty payment. Payment of a royalty might be triggered in the circumstance, for example, where a costumed employee in scene 102 appears in a picture wearing a cartoon character costume that has been licensed from an outside party. Thus, tagging filter 142 can search pictures 106 a through 110 a for images of a cartoon character that are protected by copyright or fall under third party licenses. In doing so, tagging filter 142 generates pictures and metadata tags 106 b through 116 b, and additionally generates new metadata tags 118 b and 120 b. In this example, picture 108 b is associated with metadata tag 118 b, and picture 110 b is associated with metadata tag 120 b. Metadata tags 118 b and 120 b indicate that associated pictures 108 b and 110 b contain an image that triggers royalty payment upon later publication.

After being generated by tagging filter 142, pictures and metadata tags 106 b through 120 b can be evaluated by grouping filter 144. Unlike tagging filter 142, grouping filter 144 does not associate or dissociate metadata tags from pictures. Instead, grouping filter 144 separates pictures into different groups based on the information in metadata tags associated with those pictures.

In the present embodiment, grouping filter 144 is configured to separate pictures associated with metadata tags that indicate royalty-triggering imagery from pictures that are not so associated. Thus, in evaluating pictures and metadata tags 106 b through 120 b, grouping filter 144 generates a first group including picture 106 c and associated metadata tag 112 c, and a second group including pictures 108 c and 110 c and associated metadata tags 114 c through 120 c.

After being generated by grouping filter 144, picture 106 c and associated metadata tag 112 c can be, for example, stored in MALM 140 for later use. In the meantime, pictures 108 c and 110 c and associated metadata tags 114 c through 120 c can be evaluated by executive 146. Unlike tagging and grouping filters 142 and 144, executive 146 has abilities that extend beyond associating and dissociating metadata tags and separating pictures into groups; for example, executive 146 can modify or delete a picture.

In the present embodiment, executive 146 is implemented as a person operating a computer terminal, and evaluates pictures according to theme park quality guidelines. Executive 146 may decide to delete picture 108 c if the image is blurred or partially obscured, and retain picture 110 c because the image has no such impairment. In deleting picture 108 c and associated metadata tags 114 c and 118 c, executive 146 generates deleted picture 108 d and associated deleted metadata tags 114 d and 118 d. Deleted picture 108 d may be erased from a storage medium in MALM 140, or may be retained in some inactive capacity. Executive 146 retains picture 110 c and associated metadata tags 116 c and 120 c by generating picture 110 d and associated metadata tags 116 d and 120 d. Executive 146 may then dissociate metadata tags 116 d and 120 d and export picture 110 d for publication and royalty payment, as depicted by exported picture 110 e.

Thus, in MALM 140 of FIG. 1, the allocation of tasks between tagging filter 142, grouping filter 144, and executive 146 allows for efficient management of the lifecycles of pictures 106 a through 110 a. Utilizing a clearly defined set of procedures, MALM 140 stores picture 106 a (at 106 c) for later use, deletes low-quality picture 108 a (at 108 d), and exports for publication and royalty payment picture 110 a (at 110 e).

FIG. 2 shows a diagram of system 200 including media asset lifecycle manager (MALM) 240 for managing the lifecycle of media assets, according to another embodiment of the present invention. In operation, media assets pictures 202 a and 204 a, videos 206 a and 208 a, and associated metadata tags 210 a through 216 a are imported into MALM 240 utilizing, for example, means similar to those used to import media assets into MALM 140. Prior to importation, pictures 202 a and 204 a, videos 206 a and 208 a, and associated metadata tags 210 a through 216 a may have been generated by, for example, a picture and video-producing camcorder (not shown), or by more than one source.

In the present embodiment, pictures 202 a and 204 a and videos 206 a and 208 a are associated with metadata tags 210 a through 216 a. In particular, picture 202 a is associated with metadata tag 210 a, picture 204 a is associated with metadata tag 212 a, video 206 a is associated with metadata tag 214 a, and video 208 a is associated with metadata tag 216 a. Metadata tags 210 a through 216 a contain information about what kind of media asset each is associated with, and may contain other information such as, for example, a timestamp. After importation, MALM 240 can manage the lifecycles of pictures 202 a and 204 a and videos 206 a and 208 a by using filters 230 through 236 and an executive 238.

After being imported into MALM 240, pictures 202 a and 204 a, videos 206 a and 208 a, and associated metadata tags 210 a through 216 a can be evaluated by grouping filter 230. Grouping filter 230 can be implemented as, for example, software executing on a computer processor (not shown), or as a human using a computer terminal (not shown). Like grouping filter 144 of system 100, grouping filter 230 separates media assets into different groups based on the information in metadata tags associated with those media assets.

In the present embodiment, grouping filter 230 is configured to separate picture media assets from video media assets. Thus, after evaluating pictures 202 a and 204 a, videos 206 a and 208 a, and associated metadata tags 210 a through 216 a, grouping filter 230 generates group 222 a including corresponding pictures 202 b and 204 b and associated metadata tags 210 b and 212 b, and group 224 a including corresponding pictures 206 b and 208 b and associated metadata tags 214 b and 216 b. Group 222 a is a group of picture media assets, and group 224 a is a group of video media assets.

After being sorted into group 222 a, pictures 202 b and 204 b and associated metadata tags 210 b and 212 b can be evaluated by tagging filter 232. Tagging filter 232 may evaluate media assets and associated metadata tags in a variety of ways. For example, tagging filter 232 may evaluate picture 202 b and associated metadata tag 210 b to determine if one or more additional metadata tags should be associated, or if already-associated metadata tag 210 b should be removed. To make such an evaluation, tagging filter 232 may utilize the information in picture 202 b, in metadata tag 210 b, or in both. Tagging filter 232 may obtain the information in picture 202 b, for example, by utilizing a computerized image processing of pictures 202 b and comparison other information or pictures a database. Alternatively, tagging filter 232 may utilize information from other sources; for example, the information in picture 204 b and metadata tag 212 b.

In the present embodiment, tagging filter 232 is configured to determine if a picture violates a decency guideline. A decency guideline might be violated, for instance, if a picture contains imagery that is inappropriate for viewing by minors. After evaluating pictures 202 b and 204 b and associated metadata tags 210 b and 212 b, tagging filter 232 generates corresponding pictures 202 c and 204 c and associated metadata tags 210 c and 212 c, as well as new associated metadata tag 218 c, in group 222 b. Metadata tag 218 c is associated with picture 202 c, and indicates that picture 202 c may contain indecent content.

Tagging filter 234 evaluates videos 206 b and 208 b and associated metadata tags 214 b and 216 b of group 224 a in a fashion similar to that utilized by tagging filter 232 on the contents of group 222 a. Tagging filter 234, in the present embodiment, is configured to determine if a video violates a decency guideline. Like the picture decency guideline applied by tagging filter 232, the video decency guideline applied by tagging filter 234 might be violated, for instance, if a video contains imagery that is inappropriate for viewing by minors. After evaluating videos 206 b and 208 b and associated metadata tags 214 b and 216 b, tagging filter 234 generates corresponding videos 206 c and 208 c and associated metadata tags 214 c and 216 c, as well as new associated metadata tag 220 c, in group 224 b. Metadata tag 220 c is associated with video 206 c, and indicates that video 206 c may contain indecent content.

Thus, the result of evaluating the contents of groups 222 a and 224 a with tagging filters 232 and 234 is corresponding groups 222 b and 224 b. MALM 240 can then proceed by evaluating the contents of groups 222 b and 224 b with grouping filter 236. Grouping filter 236, like grouping filter 230, can separate media assets into different groups based on the information in metadata tags associated with those media assets. Furthermore, grouping filter 236 can similarly be implemented as, for example, software executing on a computer processor (not shown), or as a human using a computer terminal (not shown).

In the present embodiment, grouping filter 236 is configured to separate media assets that have been associated with a metadata tag indicative of indecent content from those that have not. Thus, after evaluating metadata tags 210 c through 220 c, grouping filter 236 generates group 226 a, which includes picture 202 d, video 206 d, and associated metadata tags 210 d, 214 d, 218 d, and 220 d, and group 228 a, which includes picture 204 d, video 208 d, and associated metadata tags 212 d and 216 d. Notably, the contents of groups 226 a and 228 a do not correspond to the contents of groups 222 b and 224 b. Group 226 a is a group of media assets that have been associated with metadata tags indicative of indecent content, and group 228 a is a group of media assets that have not been so associated.

After being generated by grouping filter 236, pictures 202 d and 204 d, videos 206 d and 208 d, and associated metadata tags 210 d through 220 d can be evaluated by executive 238. Unlike tagging and grouping filters 230 through 236, executive 238 has abilities that extend beyond associating and dissociating metadata tags and separating media assets into groups; for example, executive 238 can modify or delete a media asset. Executive 238 can be implemented, for example, as software executing on a computer processor (not shown), or as a human using a computer terminal (not shown).

In this embodiment, executive 238 may perform final reviews of media assets that have been associated with metadata tags indicative of indecent content. For example, executive 238 may delete picture 202 d and associated metadata tags 210 d and 218 d, thereby generating deleted picture 202 e and associated deleted metadata tags 210 e and 218 e, upon confirming that picture 202 d contains indecent content. Deleted picture 202 e may be erased from a storage medium in MALM 140, or may be retained in some inactive capacity. In contrast, upon performing a final review of video 206 d and deciding that video 206 d is not indecent, executive 238 may opt to retain video 206 d and associated metadata tag 214 d, and delete inaccurate metadata tag 220 d, thereby generating video 206 e, associated metadata tag 214 e, and deleted metadata tag 220 e.

Thus, in MALM 240, the application of tagging and grouping filters 230 through 236 and executive 238 allows for the efficient management of the lifecycles of pictures 202 a and 204 a and videos 206 a and 208 a. Utilizing a number of steps, MALM 240 isolates potentially indecent media assets, performs a final review of those media assets, deletes indecent picture 202 a (at 202 e), and retains picture 204 a and videos 206 a and 208 a (at picture 204 d and videos 208 d and 206 e). A notable advantage of MALM 240 is that because of the work done by filters 230 through 236, executive 238 need only evaluate a small portion of the media assets originally imported into the system. Thus, executive 238 can afford to give more intense scrutiny to suspect media assets, or can spend less overall resources evaluating suspect media assets. In contrast, present conventional methods and systems for achieving similar results apply executive review in an ad-hoc, inefficient fashion.

FIG. 3 shows flowchart 300 of an exemplary method of managing the lifecycles of media assets. Certain details and features have been left out of flowchart 300 that are apparent to a person of ordinary skill in the art. For example, a step may comprise one or more substeps or may involve specialized equipment or materials, as known in the art. While steps 310 through 360 indicated in flowchart 300 are sufficient to describe one embodiment of the present invention, other embodiments of the invention may utilize steps different from those shown in flowchart 300.

In step 310 of flowchart 300, a system for managing the lifecycles of media assets imports one or more media assets. Some embodiments of the present invention may be capable of managing only one media asset at once, while other embodiments may be capable of managing many media assets at once. Some embodiments of the present invention may store hard copies of imported media assets, while other embodiments may store imported media assets on digital storage devices such as hard disk drives. A media asset imported into the system can be a picture, a video, an audio recording, or any other conceivable instance of media.

Moving on with flowchart 300, step 320 comprises evaluating the imported media asset or assets with one or more tagging filters to determine if metadata tags should be associated with them. Tagging filters can be implemented in the media asset lifecycle management system by any mechanism capable of examining a media asset against a set of criteria. For example, in one embodiment, a tagging filter may be a computer program running in software that searches digital picture files for copyrighted imagery. If a tagging filter determines that a particular media asset fails to meet its evaluation criteria, no further action needs to be taken, but if a particular media asset does meet the evaluation criteria of the filter, an association step may be taken.

Step 330 of flowchart 300 comprises associating a metadata tag with a media asset, after a tagging filter has determined that such an association is appropriate. For example, if a tagging filter determines that a particular media asset contains copyrighted material, then a metadata tag indicating that fact will be associated with the media asset. For example, an association step might entail imprinting a photograph with a human-readable copyright stamp, or might entail linking a digital picture record with a metadata tag record in a database. By associating a metadata tag with a media asset, persistent information can be tied to the media asset as it is processed through the media asset lifecycle management system.

Moving on with flowchart 300, step 340 comprises evaluating media assets according to the metadata tags they are associated with, if any, by using a grouping filter. Grouping filters can be implemented in the media asset lifecycle management system by any mechanism capable of examining a metadata tag against a set of criteria. Thus, in one embodiment, a grouping filter may be implemented as an optical scanner for scanning tagged photographs, while in another embodiment a grouping filter may be implemented as a database query.

Step 350 of flowchart 300 comprises grouping media assets and associated metadata tags, if any, after evaluating them with a grouping filter. In one embodiment, for example, media assets may be grouped with a mechanical sorter for sorting photographs into different stacks. In another embodiment, media assets may be grouped with a database query that outputs two or more sets of database records.

Step 360 of flowchart 300 comprises evaluating grouped media assets and associated metadata tags by utilizing an executive. An executive may be implemented as any mechanism capable of performing executive tasks, such as deletion or exportation from the media asset lifecycle management system. After evaluation, an executive may delete some or all of the media assets in a group, or place evaluated media assets into new or different groups. For example, in one embodiment an executive may be a person who examines a stack of photos bearing imprinted copyright tags, while in another embodiment an executive may be a database query that has record deletion privileges. By evaluating media assets in specific groups, instead of evaluating media assets in entire sets, an executive can conserve resources or give each media asset more intense scrutiny.

Thus, the present application discloses a method and system for managing the lifecycles of media assets. By importing media assets into a system for managing their lifecycles, one embodiment of the present invention collects those media assets for convenient review. By utilizing tagging and grouping filters in advantageous combinations, media assets that have been imported can be evaluated and sorted into groups of varying characteristics, for further efficient evaluation by additional tagging and grouping filters or by executives. In various embodiments of the present invention, executives may override the prior evaluations of filters, delete media assets, or export media assets from the lifecycle management systems for external use.

From the above description of the invention it is manifest that various techniques can be used for implementing the concepts of the present invention without departing from its scope. Moreover, while the invention has been described with specific reference to certain embodiments, a person of ordinary skill in the art would recognize that changes can be made in form and detail without departing from the spirit and the scope of the invention. It should also be understood that the invention is not limited to the particular embodiments described herein, but is capable of many rearrangements, modifications, and substitutions without departing from the scope of the invention. 

1. A system for managing the lifecycles of one or more media assets, the system comprising: one or more metadata tags, the one or more metadata tags being configured to associate with the one or more media assets; one or more tagging filters, the one or more tagging filters being configured to associate the one or more metadata tags with the one or more media assets; and one or more grouping filters, the one or more grouping filters being configured to group the one or more media assets according to the one or more metadata tags associated by the one or more tagging filters with the one or more media assets to generate media asset groups.
 2. The system of claim 1, further comprising one or more executives, the executives being configured to execute an action on the one or more media assets in the one or more media asset groups.
 3. The system of claim 2, wherein the one or more executives are implemented in software for execution by a computer.
 4. The system of claim 1, wherein the one or more tagging filters are implemented in software for execution by a computer.
 5. The system of claim 1, wherein the one or more grouping filters are implemented in software for execution by a computer.
 6. The system of claim 1, wherein the one or more metadata tags can be configured to contain media asset timestamp information.
 7. The system of claim 1, wherein the one or more media assets are pictures.
 8. The system of claim 1, wherein the one or more media assets are videos.
 9. The system of claim 1, wherein the one or more media assets are audio recordings.
 10. A method for managing the lifecycles of one or more media assets, the method comprising: importing the one or more media assets into a system for managing the lifecycles of the one or more media assets; determining one or more metadata tags for association with the one or more media assets by evaluating the one or more media assets with one or more tagging filters; associating the one or more metadata tags with the one or more media assets after determining one or more metadata tags for association with the one or more media assets; and grouping the one or more media assets according to the one or more metadata tags associated with the one or more media assets by evaluating the one or more metadata tags with one or more grouping filters to generate one or more media asset groups.
 11. The method of claim 10, further comprising importing one or more external metadata tags associated with the one or more media assets.
 12. The method of claim 11, further comprising grouping the one or more media assets according to the one or more metadata tags and the one or more external metadata tags associated with the one or more media assets to generate the one or more media asset groups.
 13. The method of claim 10, further comprising executing an action on the one or more media assets in the one or more media asset groups.
 14. The method of claim 10, wherein one of the one or more tagging filters is configured to evaluate the one or more media assets by inspecting the one or more media assets for copyrighted material.
 15. The method of claim 10, wherein one of the one or more grouping filters is configured to evaluate the one or more media assets by inspecting the one or more media assets for content that violates a decency or obscenity policy.
 16. The method of claim 10, wherein the one or more tagging filters are implemented in software for execution by a computer.
 17. The method of claim 10, further comprising utilizing a camera to create the one or more media assets.
 18. The method of claim 10, wherein the one or more media assets are pictures.
 19. The method of claim 10, wherein the one or more media assets are videos.
 20. The method of claim 10, wherein the one or more media assets are audio recordings. 